|
![](/i/fill.gif) |
crss {}
I like abreviation. I'll vote yea on the short keywords too, and the
underscore removal.
Any idea about making spaces available between keywords? Plausible
(doable I don't know) to make a keyword recognisable (oops, my Canadian
sp.) which goes as a pair of words or more? ie. max trace level, or do
they have to be a solid string in the C programming language
definitions? Hey, how would this be for something in POV-Ray script too?
Good idea, but not possible?
Mental note: too many questions at once may appear to inquisitive ;)
Ron Parker wrote:
>
> On Tue, 23 Feb 1999 11:36:14 +0200, Margus Ramst <mar### [at] peak edu ee> wrote:
> >I agree with the abovesaid.
> >I really don't have a problem with underscores; you could make your keywords
> >start with sth. unique like photon_* so they would be unlikely to conflict
> >with variables. However, it's easy for people to change their variables.
> >Only please, avoid mega-long keywords! I can rarely write max_trace_level in
> >one go without typos.
>
> What about catmull_rom_sphere_sweep? :)
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/POVring.htm
mailto:inv### [at] aol com?PoV
Post a reply to this message
|
![](/i/fill.gif) |